This is a good fix (with tests added) although having the parameters optional is turning out to be a big hassle . So many extra cases and bugs just so you don't have to type {},.

I know... :-(. I'm 50/50 on it right now. I'll have tests for this shortly. I actually need this fix asap.

If you're really that much against typing {}, 😉
Tests should be pretty easy once those are in I'll push a new release.

This is probably related to feathersjs/feathers#113. I think that if we always normalize and validate method parameters beforehand all hooks should work.

@daffl yes it seems to be causing a lot work arounds the fact that params can be optional. We should make it required that you pass at least {}.

I agree. As @marshallswain pointed out though, it is still easy to break the server by sending the wrong arguments through the socket.

Ya I saw that 😢. Let's make it required and then we can emit nice errors telling people that they need to at least pass {}. I'm now caught up on sleep and looking to do some coding this afternoon/evening.

We should actually use the argument normalization from feathers-commons and perform argument normalization on this line

This has been done and is released in version 1.1.0.